Hello I am trying to add deployment permissions to our YAML deployment specs and I am getting the following error
Bamboo YAML import failed: Document structure is incorrect: Found following unused properties: QA, Staging, environments, Production, Sandbox, release-naming, deployment / source-plan
I have tried many different variations to add the deployment permissions but I am obviously doing something wrong, using bamboo version 7.03 with a spec similar to the below.
version: 2
deployment:
name: Deployment Project
source-plan: APROJ
release-naming:
next-version-name: Deployment-${bamboo.buildNumber}
applies-to-branches: false
environments:
- Sandbox
- QA
- Staging
- Production
deployment-permissions:
- users:
- auser
default-environment-permissions:
- users:
- auser
groups:
- bamboo-dev
permissions:
- view
- edit
- deploy
Sandbox:
tasks:
- artifact-download
- script:
interpreter: /bin/sh
scripts:
- docker-compose run --rm web bundle exec cap sandbox deploy
final-tasks:
- script:
interpreter: /bin/sh
scripts:
- docker-compose down
- docker system prune --volumes -f
- clean
QA:
tasks:
- artifact-download
- script:
interpreter: /bin/sh
scripts:
- docker-compose run --rm web bundle exec cap qa deploy
final-tasks:
- script:
interpreter: /bin/sh
scripts:
- docker-compose down
- docker system prune --volumes -f
- clean
Staging:
tasks:
- artifact-download
- script:
interpreter: /bin/sh
scripts:
- docker-compose run --rm web bundle exec cap staging deploy
final-tasks:
- script:
interpreter: /bin/sh
scripts:
- docker-compose down
- docker system prune --volumes -f
- clean
Production:
tasks:
- artifact-download
- script:
interpreter: /bin/sh
scripts:
- docker-compose run --rm web bundle exec cap production deploy
final-tasks:
- script:
interpreter: /bin/sh
scripts:
- docker-compose down
- docker system prune --volumes -f
- clean
Many thanks in advance
Deployment permissions should be kept at separate YAML document, like this:
```
version: 2
deployment:
name: Deployment Project
source-plan: APROJ
release-naming:
next-version-name: Deployment-${bamboo.buildNumber}
applies-to-branches: false
environments:
- Sandbox
- QA
- Staging
- Production
Sandbox:
tasks:
- artifact-download
- script:
interpreter: /bin/sh
scripts:
- docker-compose run --rm web bundle exec cap sandbox deploy
final-tasks:
- script:
interpreter: /bin/sh
scripts:
- docker-compose down
- docker system prune --volumes -f
- clean
QA:
tasks:
- artifact-download
- script:
interpreter: /bin/sh
scripts:
- docker-compose run --rm web bundle exec cap qa deploy
final-tasks:
- script:
interpreter: /bin/sh
scripts:
- docker-compose down
- docker system prune --volumes -f
- clean
Staging:
tasks:
- artifact-download
- script:
interpreter: /bin/sh
scripts:
- docker-compose run --rm web bundle exec cap staging deploy
final-tasks:
- script:
interpreter: /bin/sh
scripts:
- docker-compose down
- docker system prune --volumes -f
- clean
Production:
tasks:
- artifact-download
- script:
interpreter: /bin/sh
scripts:
- docker-compose run --rm web bundle exec cap production deploy
final-tasks:
- script:
interpreter: /bin/sh
scripts:
- docker-compose down
- docker system prune --volumes -f
- clean
---
version: 2
deployment:
name: Deployment Project
source-plan: APROJ
deployment-permissions:
- users:
- auser
permissions:
- view
default-environment-permissions:
- users:
- auser
groups:
- bamboo-dev
permissions:
- view
- edit
- deploy
```
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.