bamboo-specs deployment permission

unknown

I have this Deployment and I'm trying to add a permission for this deployment

---
version: 2
deployment:
name: deploy_name
source-plan: key-key

release-naming:
next-version-name: release-${bamboo.buildNumber}

environments:
- Test

Test:
tasks:
- clean
- artifact-download:
destination: .
- script:
- '#!/bin/bash'
- echo 'ok'

---
version: 2
deployment: deploy_name

environment-permissions:
- Test:
- users:
- administrator
groups:
- group_name
permissions:
- view
- deploy

 

but I'm getting the error below:

Bamboo YAML import failed: Document structure is incorrect: deployment: Element is of wrong type. Expected MapNode, found StringNode

How I solve this problem? because in the documentation say fo create in different documents.

I tried putting in the same document and get other error:

Bamboo YAML import failed: Invalid format of the YAML file: mapping values are not allowed here
 in 'reader', line 94, column 24:
    environment-permissions:
                           ^

 

Rafael Pinto Sperafico_35quns

Hi @[deleted],

It is important to notice that Bamboo Specs YAML Version 2.0 was introduced in Bamboo v6.9 as described in https://confluence.atlassian.com/bamboo/bamboo-6-9-release-notes-969521942.html.

If you are running Bamboo v6.9 or above, then the 1st error:

Bamboo YAML import failed: Document structure is incorrect: deployment: Element is of wrong type. Expected MapNode, found StringNode

relates to a deployment without a name:

---
version: 2
deployment: DEPLOYMENT NAME

Please, refer to Bamboo YAML documentation https://docs.atlassian.com/bamboo-specs-docs/6.9.0/specs.html?yaml#deployment-permissions as it provides you with more information on how to set up Deployment and Environment permissions.

Then, the subsequent error:

Bamboo YAML import failed: Invalid format of the YAML file: mapping values are not allowed here
 in 'reader', line 94, column 24:
    environment-permissions:
                           ^

Relates to a missing part in the documentation where deployment-permissions must be declared. Therefore, you should be running the following instead:

---
version: 2
deployment: DEPLOYMENT NAME

deployment-permissions: 
  - users:
    - admin

environment-permissions:
  - Test:
    - users:
      - admin

I have commented on this missing information internally and it should be amended in the documentation soon.

Kind regards,
Rafael