Coder Social home page Coder Social logo

tastefulelk / iam-legend Goto Github PK

View Code? Open in Web Editor NEW
149.0 2.0 7.0 3.01 MB

IAM policy actions autocomplete, documentation & wildcard resolution for VS Code

License: MIT License

JavaScript 20.34% TypeScript 79.10% Shell 0.56%
aws aws-sam cdk cloudformation iam serverless serverless-framework terraform visual-studio-extension

iam-legend's Introduction

Visual Studio Marketplace Version Visual Studio Marketplace Rating Stars Visual Studio Marketplace Downloads

IAM Legend

AWS IAM actions autocomplete, documentation and wildcard resolution for Visual Studio Code.

Supports Serverless Framework, AWS SAM, CloudFormation and Terraform.

Features

  • Autocomplete for all IAM services & actions

service suggestions

  • Inline documentation for each action, including what Resources and Condition Keys they support as well as any Dependent Actions

action suggestions and documentation

  • Wildcard support when hovering an action definition to easily see exactly what action(s) will be granted

docs for multiple actions when hovering action with wildcard

Contributions

Feedback, suggestions, bug reports or any other kind of contributions are very welcome! You can find the source here!

Author

Sebastian Bille

iam-legend's People

Contributors

adriencaccia avatar semantic-release-bot avatar service-bot avatar tastefulelk avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar

iam-legend's Issues

Make case-insensitive

Many parts of IAM policies are not case sensitive. Like action names and condition context keys. However it appears iam-legend only provides mouseover information if the action name matches the casing of the API definitions:
Works:
image

Doesn't work with different-cased service prefix, doesn't recognize it as an IAM action to consider:
image

Doesn't work with different-cased action, but at least recognizes this is an IAM service:
image

I think the extension should be case-insensitive in these situations. Thanks!

Support Typescript configuration files

Hey @TastefulElk !

First, huge thanks for this amazing extension, it is a real life (time) saver πŸ™

However, it does not work with Typescript serverless framework configuration files (supported since v1.72.0).

Example:

import type { AWS } from '@serverless/typescript';

const serverlessConfiguration: AWS = {
  ...
  provider: {
    ...
    iamRoleStatements: [{
      Effect: "Allow",
      Action: ['dynamodb:*'],
    }],
  },
};

module.exports = serverlessConfiguration;

I took a crack at it and submitted a PR πŸ˜‰

The automated release is failing 🚨

🚨 The automated release from the master branch failed. 🚨

I recommend you give this issue a high priority, so other packages depending on you can benefit from your bug fixes and new features again.

You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can fix this πŸ’ͺ.

Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.

Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the master branch. You can also manually restart the failed CI job that runs semantic-release.

If you are not sure how to resolve this, here are some links that can help you:

If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.


Empty ovsx personal access token specified.

Unfortunately this error doesn't have any additional information. Feel free to kindly ask the author of the semantic-release-vsce plugin to add more helpful information.


Good luck with your project ✨

Your semantic-release bot πŸ“¦πŸš€

v2 versions overwrite v1-versions actions

v1 versions of services use the same service-prefix as the v2 version - this means the v1 actions gets overwritten by the v2 actions

example: #8
Greengrass v2 overwrites Greengrass v1 actions as they share the same service-prefix greengrass

Question with Terraform

It is quite possible I am just not enabling something, but I can't seem to get this to work while writing Terraform code. I don't see lookups whether I am writing the policy jsonecode inline, or with more traditional policy creation using the data block aws_iam_policy_document. Is there a specific way the extension needs to be enabled to work with TF files? It looks great otherwise, something I feel we could use with all the new folks we have entering into the IaC world.

The automated release is failing 🚨

🚨 The automated release from the master branch failed. 🚨

I recommend you give this issue a high priority, so other packages depending on you can benefit from your bug fixes and new features again.

You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can fix this πŸ’ͺ.

Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.

Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the master branch. You can also manually restart the failed CI job that runs semantic-release.

If you are not sure how to resolve this, here are some links that can help you:

If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.


Invalid vsce token. Additional information:

Error: Command failed with exit code 1: vsce verify-pat
ERROR The Personal Access Token verification has failed. Additional information:

Error: The user with identifier 'c0641ee7-6960-4381-8e18-32eb017d71ec' does not exist.

Unfortunately this error doesn't have any additional information. Feel free to kindly ask the author of the semantic-release-vsce plugin to add more helpful information.


Good luck with your project ✨

Your semantic-release bot πŸ“¦πŸš€

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    πŸ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. πŸ“ŠπŸ“ˆπŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❀️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.