Investigate using an allowlist for IronBank schema fields
Proposal
When working on https://gitlab.com/gitlab-org/customers-gitlab-com/-/merge_requests/3888, @rcobb proposed the idea of using an allowlist, instead of or in addition to a denylist (excluded_fields.yml
). This would allow us to be more intentional about the resource models used by CustomersDot. It would also allow us to ignore most custom fields by default without having to specify them.
Since this would involve a change in addition the default IronBank excluded_fields.yml
feature, we decided to work this into a v2 of the changes introduced in #2831 (closed).
Follow-up
The following discussion from !3888 should be addressed:
-
@tyleramos started a discussion: (+3 comments) @rcobb Would you mind reviewing this MR when you have a time? I decided not to assign Vij as I've picked on him a few times lately. Thanks in advance!
As I mentioned in the issue description, you can probably focus your review just on the first commit. The second commit contains all the re-recorded VCR cassettes. Let me know if you have any questions.