| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
…ary_data_in_datastore Update sensors to store temporary data in the datastore
When token is "" (by default), it's considered as a string and thereby is passed to GitHub:
Error message:
github.GithubException.BadCredentialsException: 401 {u'documentation_url': u'https://developer.github.com/v3', u'message': u'Bad credentials'}
Let's make it more user-friendly and less strict
* look up from config had many possibilities of key error. * also, some code to keep the sensor running even if some config is removed.
* Why? Because without a repository there is nothing that can be done.
Add ReleaseEvent to GithubRepositorySensor [github]
Fix lookups from config.
Action name: create_issue Parameters: * title (string) * description (string, optional) * repo (string) * user (string) * assignee (string, optional) Updated README and increased pack version number to 0.2
… default whitelisted events
…if one is not explicitly provided in the config.
…causig issues for new actions
… deployments in GitHub pack. - Increase version to 0.5 (and update CHANGES.rst). - Add new actions - create_deployment - create_deployment_status - create_release - get_deployment_statuses - get_user - latest_release - list_deployments - list_releases - store_enterprise_oauth_token - store_oauth_token - Migrate to config.schema.yaml (and remove config.yaml). - Add requests session object, request and token helpers to base class.
- Add license headers. - Support online and enterprise GitHub (with a default) for the new actions. - Add tests (currently only that the action loads).
- Make store_oauth_token action use github_type like the other actions. - Add missing description's (and correct others). - Remove store_enterprise_oauth_token alias and action YAML. - Add test_action_aliases tests for all aliases.
- Add check_deployment_env action. - Increase pack version number. - Add deployment_event workflow. - Add tests for check_deployment_env - Update tests/fixtures/full.yaml to include deployment_environment. - Add workabout to finding usernames that contain `.` when GitHub Enterprise replaces them with `-` to `BaseGithubAction_get_user_token`.
- fix spelling mistakes. - Rename rule `deployment_event_webhook` to `deploy_pack_on_deployment_event`.
* ## 1.2.0 * Add new ``github.get_contents`` action which allows user to retrieve file and repository contents. * Add new ``github.create_file`` action which allows user to create new files in repositories. * Add new ``github.update_file`` action which allows user to update existing files in repositories. * Bump libs version in requirements.txt * fix typo * token/password must be secret in pack's config * fixing config schema's default token reference to datastore * changelog update * config schema update
…Actions Repository actions
| Back | FazBrowse Home | New Git URL |
Do not merge until the Exchange transition is finalized
This PR makes use of the new packs.install syntax introduced in StackStorm 2.1: we'll make deployment_event (a rule+workflow combination for continuous deployment of StackStorm packs) use the new syntax.
Packs can be installed with nothing but a git URL now, with the pack name read from pack.yaml. so we can strip some unnecessary parameters and just feed the URL instead.
A specific version (=git ref) of a pack can be installed by appending =<version> to the pack name/URL. We’ve made a conscious effort to make the ref as generic as possible, so you can actually use branches, tags, version tags with the appended v, and of course commit SHAs in place of <version>.
Now the workflow has less code and supports more things. Profit!
@jjm, look! I promised it’ll be magical, didn’t I? 😛