[discussion] Other namespace support

[mbarneyjr]

There are some CloudFormation resources that do not conform to the AWS::Service::Resource pattern. According to the CloudFormation FAQ, there could be resources that look like this: Alexa::*. In fact, there's an Alexa::ASK::Skill resource, that I don't believe former would be able to stub out for you, since it expects only the second two parts of the resource type and fills in the AWS for you

My first thoughts are:

• to allow defining the full resource name as a parameter (i.e. former Alexa::ASK::Skill or former AWS::S3::Bucket)
• to look for each special case as the first argument (currently only alexa I believe, so former alexa ask skill would function just like former aws s3 bucket or former s3 bucket)
• whatever you decide is best for user experience

I came across this issue because I would like to implement autocomplete/tab-completion for the former cli. However if there will be another way to use former, such as the above suggestions, I would like to know what that is before I begin work implementing autocomplete

So this issue is to flesh out what the user experience should be for resources that are not under the AWS::* namespace

Thoughts @flomotlik?

[flomotlik]

How about we do it with 2 or 3 arguments, so if you enter only 2 AWS is used, if you enter 3 the first one is the namespace?

Autocomplete would be amazing. Been on the list for a while but haven't had time to get around to it yet.

[mbarneyjr]

The current implementation supports 3 arguments, for sub properties:

former iam user loginprofile

[flomotlik]

Hmm, you're right. How about we do a two step lookup, first we see if we can find the resource with the AWS prefix and if that doesn't exist we look it up without the AWS Namespace and use the first argument as namespace? Its pretty unlikely to happen as its only so few resources.

If you have another proposal open to any other ideas.