Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

aws ec2 describe-network-interface-attribute #558

Closed
julieso opened this issue Dec 15, 2013 · 2 comments · Fixed by boto/botocore#327
Closed

aws ec2 describe-network-interface-attribute #558

julieso opened this issue Dec 15, 2013 · 2 comments · Fixed by boto/botocore#327
Labels
bug This issue is a bug.

Comments

@julieso
Copy link
Contributor

julieso commented Dec 15, 2013

For consistency, I'd expected this command to support an option --attribute (as commands like describe-image-attribute and describe-instance-attribute do)

aws ec2 describe-network-interface-attribute --network-interface-id eni-e5aa89a3 --attribute
Unknown options: --attribute

In trying to use options like --description and --source-dest-check, it appears that they require a parameter. That seems odd, as I'm not trying to set these attributes. What arguments are expected here?

aws ec2 describe-network-interface-attribute --network-interface-id eni-e5aa89a3 --description
usage: aws [options] [parameters]
aws.cmd: error: argument --description: expected one argument

aws ec2 describe-network-interface-attribute --network-interface-id eni-e5aa89a3 --source-dest-check
usage: aws [options] [parameters]
aws.cmd: error: argument --source-dest-check: expected one argument
@sjones4
Copy link

sjones4 commented Jul 22, 2014

I also ran into this issue, other VPC attribute commands work as expected (e.g. describe-vpc-attribute)

It is still possible to get the attribute values by describing the network interface.

jamesls added a commit to jamesls/botocore that referenced this issue Jul 28, 2014
@jamesls
Update EC2 model to the latest version
3c8188e 
This fixes an issue where the DescribeNetworkInterfaceAttribute
input was incorrect.

Fixes aws/aws-cli#558
@jamesls jamesls mentioned this issue Jul 28, 2014
Merged
@jamesls
Copy link
Member

jamesls commented Jul 28, 2014

Looks like our model was incorrect. I've updated this here: boto/botocore#327

Closing in favor of the botocore PR.

@jamesls jamesls closed this as completed Jul 28, 2014
thoward-godaddy pushed a commit to thoward-godaddy/aws-cli that referenced this issue Feb 12, 2022
@heitorlessa @sanathkr
fix(init): Improve current init samples around docs and fixes (aws#558)
48f8b1f
thoward-godaddy pushed a commit to thoward-godaddy/aws-cli that referenced this issue Feb 12, 2022
@jfuss
Release: 0.6.0 Release (aws#636)
87a4577 
* fix: Functional tests must run on localhost to work in Windows (aws#552)

* fix: spacing typo in Log statement in start-lambda (aws#559)

* docs: Fix syntax highlighting in README.md (aws#561)

* docs: Change jest to mocha in Nodejs init README (aws#564)

* docs: Fix @mhart link in README (aws#562)

* docs(README): removed cloudtrail, added SNS to generate-event (aws#569)

* docs: Update repo name references (aws#577)

* feat(debugging): Fixing issues around debugging Golang functions. (aws#565)

* fix(init): Improve current init samples around docs and fixes (aws#558)

* docs(README): Update launch config to SAM CLI from SAM Local (aws#587)

* docs(README): Update sample code for calling Local Lambda Invoke (aws#584)

* refactor(init): renamed handler for camel case, moved callback call up (aws#586)

* chore: aws-lambda-java-core 1.1.0 -> 1.2.0 for java sam init (aws#578)

* feat(validate): Add profile and region options (aws#582)

Currently, `sam validate` requires AWS Creds (due to the SAM Translator).
This commits adds the ability to pass in the credientials through a profile
that is configured through `aws configure`.

* docs(README): Update README prerequisites to include awscli (aws#596)

* fix(start-lambda): Remove Content-Type Header check (aws#594)

* docs: Disambiguation "Amazon Kinesis" (aws#599)

* docs: Adding instructions for how to add pyenv to your PATH for Windows (aws#600)

* docs: Update README with small grammar fix (aws#601)

* fix: Update link in NodeJS package.json (aws#603)

* docs: Creating instructions for Windows users to install sam (aws#605)

* docs: Adding a note directing Windows users to use pipenv (aws#606)

* fix: Fix stringifying λ environment variables when using Python2 (aws#579)

* feat(generate-event): Added support for 50+ events (aws#612)

* feat(invoke): Add region parameter to all invoke related commands (aws#608)

* docs: Breaking up README into separate files to make it easier to read (aws#607)

* chore: Update JVM size params to match docker-lambda (aws#615)

* feat(invoke): Invoke Function Without Parameters through --no-event (aws#604)

* docs: Update advanced_usage.rst with clarification on --env-vars usage (aws#610)

* docs: Remove an extra word in the sam packaging command (aws#618)

* UX: Improves event names to reflect Lambda Event Sources (aws#619)

* docs: Fix git clone typo in installation docs (aws#630)

* docs(README): Callout go1.x runtime support (aws#631)

* docs(installation): Update sam --version command (aws#634)

* chore(0.6.0): SAM CLI Version bump (aws#635)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug This issue is a bug.
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Update EC2 model to the latest version jamesls/botocore
3 participants
@jamesls @sjones4 @julieso