Project Descriptor Domains RFC

[hone]

No description provided.

[hone]

Feedback from @jromero during the platform subteam sync:

• add api field under [project] or the top level
• clarify that api field is optional for reverse domain namespaces

[hone]

From WG today: need to solve the top level domain issue. By using [project], it squats on the ".project" TLD. _ can be used in bare TOML keys that aren't allowed in domain names.

[jkutner]

I propose special casing the project TLD to resolve the issue.

1. We forbid the project table from being customized (thus, you cannot add keys to [project] or [project.mydomain]
2. As an escape hatch, we allow ["project.mydomain"] and interpret it as project.mydomain table.

Optionally, we forbid all TLD tables. This means that an org owning .google cannot create [google] key = "value", but it prevents confusion when [google] is alongside [project]

[hone]

@jkutner as discussed in the WG, forbidding just TLDs doesn't really solve the problem b/c what if I have [project.foo]. We're just squatting on the entire TLD.

[Malax]

Alternatively, we could define that the root level of this TOML does not use reverse domain keys and move them under a generic config (or similar) key. This would allow us to use descriptive keys for things that are generic (such as [project]) and still allow folks using the .project TLD to use this feature without workarounds.

This would also allow us to keep the build key if we'd like to keep it.

Example:

[project]
id = ""
name = ""
# ...

[config.com.example]
awesome = "sauce"

I'm not sure how much I personally like this, but it seems to be a viable alternative.

[jromero]

@buildpacks/platform-maintainers - please create issues for this. (update parsing of project.toml)

[sclevine]

@buildpacks/implementation-maintainers @buildpacks/distribution-maintainers needs issues

[jromero]

@nebhale I see you added the issues-created/core but not finding a spec issue. If I'm not mistaken this should have one since it's updating the project descriptor spec, right?

[sclevine]

@jromero to create issue and merge