How do I properly handle secrets with Bamboo 6.2 onwards

[Ishika Khanna]

In Bamboo versions which support Specs, how do I correctly handle secrets in my build plans? Storing them in plain text in the repository seems like bad practice.

[arslan ahmad]

Discover the complete menu of your favorite restaurants in one place. From breakfast bites to dinner delights, BJ Menu brings you updated prices, tasty options, and quick choices making your food decisions easier than ever.

[Asad]

Explore the complete Bruegger’s Bagels menu and prices up-to-date for 2025. Explore the menu of fresh bagels, breakfast sandwiches, deli sandwiches, salads, sides, desserts, beverages, and more with calories.

[HADI KHAN KHAN]

Find the nearest burger spot within London, Oxford or Cardiff. Save time and place an order for your https://allshakeshackmenu.com/ preferred Burger, Crinkle Cut Fries and shakes made by hand from the nearest Shack

[Boris Van Hardeveld]

@Ishika Khanna @leozilla @howt723 It seems like an identical question has been asked before at https://community.atlassian.com/t5/Bamboo-questions/How-do-I-properly-handle-secrets-with-Bamboo-6-2-onwards/qaq-p/679896

Please have a look at the discussion over there. In particular, https://marketplace.atlassian.com/1221965 might interest you.

[leozilla]

I am using bambo 6.10 and have exactly the same question.

When naming them something like "password", "secret" bamboo does automatically treat them as secret data, which is good but you cannot access those values in script files which is a real problem.

One workaround is to inject them manually again via a InjectVariablesTask:

```

new ScriptTask()
        .inlineBody(format("echo 'dev_secret_access_key='${bamboo_aws_dev_secret_access_key} >> %s", AWS_PROPS_FILE)),
new InjectVariablesTask().path(AWS_PROPS_FILE).namespace("aws"),
new ScriptTask().inlineBody("rm " + AWS_PROPS_FILE)

This works but its very tedious and ugly.