Matching service errors to CloudFormation error types?

Aperta
#74 0 commenti 2 reazioni 1 assegnatario Vedi su GitHub

@ericzbeard ci sta già lavorando.

Dal 13/10/2022.

Valutazione

Questa issue non è ancora stata valutata.

Descrizione

investigating

There exists a complete mapping from all errors generated by AWS services to the types of errors that can be raised by a resource handler (defined here), though this mapping is currently implicit. There will always be users who want to create their own resources around AWS services, either because of incomplete coverage or for custom behavior. These users need to deduce the elements of this mapping themselves and then implement a matching algorithm in code, as shown in this example.

Two questions:

  1. Could the library make this easier, by providing a way for users to declaratively define the mapping and a convenience method to filter boto exceptions and raise matched CloudFormation exceptions?
  2. I think the mapping doesn't depend really ever depend on the user (not totally sure on this part), so once someone has figured it out for one service, that would be useful to all users. Could this mapping therefore be part of the library itself, and contributed to by users over time?
Lingua principale
Python
Stelle
107
Fork
46
Nessuna PR unita negli ultimi 30g

Guida per i contributori

Apri la guida per i contributori

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di aws-cloudformation/cloudformation-cli-python-plugin

Tutte le issue di aws-cloudformation/cloudformation-cli-python-plugin

Issue simili

Altre issue su Python

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.