Proposal to improve the experience of the [setup] section in fastly.toml

[JakeChampion]

When using the Fastly CLI and publishing a Fastly Compute Service for the first time, the fastly.toml [setup] section is read and the resources mentioned in the section are created and linked to the Compute Service, this is a really nice feature for starter-kits however, there’s a potential issue with the implementation which limits the usefulness of this feature.

The resources are created using the exact same name as what is defined in the [setup] section, this means that you can not run fastly compute publish more than once on the same starter-kit within the same Fastly Account, because the resource name would have already been taken when the first fastly compute publish.

Resource names don't have to be equivalent to the name that the Fastly Service wants to use, this means is that we can create a unique resource name for every resource in [setup] and then link the resources to the new Fastly Service with the name provided in the [setup] section. We could prefix the resource names with name in the [setup] section to make it simpler to find the resource within the UI/CLI/API.

If we make this change, then it means a Fastly Account can deploy the same starter-kit as many times as they like, by only changing the name field in the fastly.toml, and not having to update the resource names in the code and in the [setup] section.

[Integralist]

👋🏻 Thanks for opening this issue. I think this is a duplicate of sorts of your other ticket #770

We have an internal ticket tracking this issue already, so I'll be sure to link to this updated GitHub issue.

[kailan]

For anyone interested in providing feedback on the fastly.toml format, we've just opened a community forum thread where we welcome any input: https://community.fastly.com/t/have-your-say-on-the-future-of-fastly-toml/2785