Repository navigation
release_dir not set, release artifacts not uploaded #121
Description
The above line is the conditional for reading and setting the release_dir environment variable, which is used to determine later on if a release artifact should be created and uploaded.
The list of types is not exhaustive, and too restrictive currently:
- orchestrator
- ca-gateway
- pam
- anyca-plugin
Additional integration_type values will need to be supported:
- api-client
- library
- and more: integration-manifest.json schema
The setting of the release_dir value should not be conditional; if it is set, it should be loaded into the build environment.
Conditional checking of uploading or creating a release should happen explicitly where that needs to be evaluated, and not as a side effect of not setting this required value.
Activity
doebrowsk commentedon Jun 24, 2025
The release_dir field is now always pulled from the integration-manifest.json as of release 3.3.1, currently tagged as v3. However, this now causes issues for integrations that do not define (or need to define) that field. The action that pulls these properties from the json file needs to be updated to handle missing properties, such as allowing them to be missing unless marked required.