Skip to content
This repository has been archived by the owner on Oct 18, 2024. It is now read-only.
/ destroy-stack Public archive

GitHub action to destroy a stack in Okteto Cloud as part of your automated development workflow.

License

Notifications You must be signed in to change notification settings

okteto/destroy-stack

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

54 Commits
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

⚠️ CAUTION: DEPRECATED GITHUB ACTION ⚠️

Important Notice

🚨 This GitHub Action is Deprecated

This GitHub Action is now deprecated and will no longer receive updates or maintenance. Please consider the following points before continuing to use this action:

  1. No Future Updates: There will be no further updates, improvements, or bug fixes.
  2. Potential Security Risks: Without updates, this action may become vulnerable to security risks.
  3. Compatibility Issues: Future changes to GitHub Actions or dependencies may cause this action to break or function improperly.
  4. No Support: We will no longer provide support for any issues or questions related to this action.

Learn more about our support for GitHub Actions in our documentation.

GitHub Actions for Okteto Cloud

Automate your development workflows using Github Actions and Okteto Cloud

GitHub Actions gives you the flexibility to build an automated software development workflows. With GitHub Actions for Okteto Cloud you can create workflows to build, deploy and update your applications in Okteto Cloud.

Get started today with a free Okteto Cloud account!

Github Action for Destroying a Stack in Okteto Cloud

You can use this action to destroy a stack in Okteto Cloud as part of your automated development workflow.

Inputs

namespace

The Okteto namespace to use. If not specified it will use the namespace specified by the namespace action.

name

The name of the stack. If not specified it will use the one in your manifest file.

file

The path to the manifest file. If not specified, it will default to docker-compose.yaml or  okteto-stack.yaml.

working-directory

The working directory of the action. Defaults to the root folder of the repo.

Example usage

This example runs the login action and then destroys the stack

# File: .github/workflows/workflow.yml
on: [push]

name: example

jobs:

  devflow:
    runs-on: ubuntu-latest
    steps:
    
    - uses: okteto/login@master
      with:
        token: ${{ secrets.OKTETO_TOKEN }}
    
    - uses: okteto/namespace@master

    - name: "Destroy stack"
      uses: okteto/destroy-stack@master