Skip to content
Snippets Groups Projects
Select Git revision
  • dfb714b3dfc9c8fcef9ff82ebbcfbb114a172a21
  • master default protected
  • feat-create_little_container_for_developer
  • feat/pipeline_publish_extension
  • feat-publish_extension_on_marketplace_with_ci
  • feat-log-in
  • feat-connect_uri_handler_with_chosse_workdir_and_connection
  • feat-choose-mission-workdir
  • 10-en-tant-qu-etudiant-je-souhaite-pouvoir-lancer-une-mission-de-type-vscode-desktop-sur-mon-ide
  • new-building-way-recorder
  • fix-commit-any-challenge-type
  • recorder-push-code
  • theia-extension
  • 0.1.2
  • 0.1.1
  • 0.0.6
  • 1.4
  • 1.3
  • 1.2
  • 1.1
20 results

bash.conf

Blame
  • Chart.yaml 1.15 KiB
    apiVersion: v2
    name: cdb
    description: All applications in the cdb ecosystem
    
    # A chart can be either an 'application' or a 'library' chart.
    #
    # Application charts are a collection of templates that can be packaged into versioned archives
    # to be deployed.
    #
    # Library charts provide useful utilities or functions for the chart developer. They're included as
    # a dependency of application charts to inject those utilities and functions into the rendering
    # pipeline. Library charts do not define any templates and therefore cannot be deployed.
    type: application
    
    # This is the chart version. This version number should be incremented each time you make changes
    # to the chart and its templates, including the app version.
    # Versions are expected to follow Semantic Versioning (https://semver.org/)
    version: 0.1.0
    
    # This is the version number of the application being deployed. This version number should be
    # incremented each time you make changes to the application. Versions are not expected to
    # follow Semantic Versioning. They should reflect the version the application is using.
    appVersion: snapshot
    maintainers:
    - name: takiformation
      email: takiformation@takima.cloud