Skip to content

Github action to delete a namespace in Okteto as part of your automated development workflow

License

Notifications You must be signed in to change notification settings

exivity/okteto-delete-namespace

 
 

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

60 Commits
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

GitHub Actions for Okteto

Automate your development workflows using Github Actions and Okteto

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

Try Okteto for free for 30 days, no credit card required. Start your 30-day trial now!

Github Action for Deleting a Namespace in Okteto

You can use this action to delete a namespace in Okteto as part of your automated development workflow.

Inputs

namespace

Required The name of the Okteto namespace to delete.

log-level

Log level used. Supported values are: debug, info, warn, error. (defaults to warn)

Example usage

This example runs the context action and then deletes a namespace.

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

name: example

jobs:

  devflow:
    runs-on: ubuntu-latest
    steps:
    
    - uses: okteto/context@latest
      with:
        url: https://okteto.example.com
        token: ${{ secrets.OKTETO_TOKEN }}
    
    - name: "Delete the previews namespace"
      uses: okteto/delete-namespace@latest
      with:
        name: dev-previews-cindylopez

Advanced usage

Custom Certification Authorities or Self-signed certificates

You can specify a custom certificate authority or a self-signed certificate by setting the OKTETO_CA_CERT environment variable. When this variable is set, the action will install the certificate in the container, and then execute the action.

Use this option if you're using a private Certificate Authority or a self-signed certificate in your Okteto SH instance instance. We recommend that you store the certificate as an encrypted secret, and that you define the environment variable for the entire job, instead of doing it on every step.

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

name: example

jobs:
  devflow:
    runs-on: ubuntu-latest
    env:
      OKTETO_CA_CERT: ${{ secrets.OKTETO_CA_CERT }}
    steps:
    - uses: okteto/context@latest
      with:
        url: https://okteto.example.com
        token: ${{ secrets.OKTETO_TOKEN }}
   
    - name: "Delete the previews namespace"
      uses: okteto/delete-namespace@latest
      with:
        name: dev-previews-cindylopez

About

Github action to delete a namespace in Okteto as part of your automated development workflow

Resources

License

Stars

Watchers

Forks

Packages

No packages published

Languages

  • Shell 89.1%
  • Dockerfile 10.9%