We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Device and OS: App version: Kubernetes distro being used: Other:
It appears that you cannot override the version of the BigBang extension when importing
version
#!/usr/bin/env bash mkdir -p development mkdir -p base cat << EOF > development/zarf.yaml kind: ZarfPackageConfig metadata: name: "bigbang-development" yolo: true components: - name: bigbang required: true import: path: ../base name: bigbang extensions: bigbang: version: "2.24.0" EOF cat << EOF > base/zarf.yaml kind: ZarfPackageConfig metadata: name: "Base BigBang" components: - name: bigbang required: true extensions: bigbang: version: "2.25.0" EOF (cd development; echo "n" | zarf package create --no-progress --no-color . 2>&1 | grep extensions -A 3)
extensions: bigbang: version: 2.24.0 repo: https://repo1.dso.mil/big-bang/bigbang.git
extensions: bigbang: version: 2.25.0 repo: https://repo1.dso.mil/big-bang/bigbang.git
The workaround is just to use zarf variables, but it would be nice to not need to do that.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Environment
Device and OS:
App version:
Kubernetes distro being used:
Other:
It appears that you cannot override the
version
of the BigBang extension when importingSteps to reproduce
Expected result
Actual Result
Visual Proof (screenshots, videos, text, etc)
Severity/Priority
Additional Context
The workaround is just to use zarf variables, but it would be nice to not need to do that.
The text was updated successfully, but these errors were encountered: