atomist / sdm-local Goto Github PK

Currently produces error output

Secrets should be sourced from the environment if not provided

When running my inspection, if I change the code in a project and commit to master, it doesn't notice that code. It's still looking at an old commit.
If I restart the SDM then it inspects the latest master.

This will allow better usage patterns and experimentation

Enable different behavior within SDM programming model

This will require different ports to be set, and clients to be able to connect on different ports

If they want to take atomist hooks out, we can't require them to get an SDM running.

(is there a concept of more than one SDM adding hooks? if so, we could give them an option to remove all of them without an SDM running)

cdupuis@imac-pro:~/Desktop/generate $ slalom import --owner atomsit --repo lifecycle-automation
Cloning into 'lifecycle-automation'...
remote: Invalid username or password.
fatal: Authentication failed for 'https://github.com/atomsit/lifecycle-automation/'
Error: Command failed: git clone http://github.com/atomsit/lifecycle-automation
Cloning into 'lifecycle-automation'...
remote: Invalid username or password.
fatal: Authentication failed for 'https://github.com/atomsit/lifecycle-automation/'

Probably related to 2FA.

Use something like jetty to update goals in place rather than scrolling, mimicking lifecycle

create spring vs create spring kotlin rejects rootPackage parameter

Presently we need to configure builders to report status to the local SDM. This breaks portability between local and cloud SDMs, which is unacceptable.

Ideas:

• Have SDM passed to LocalBuilder (breaking change), using it instead of sending to Atomist in general
• Reset a global build status updater
• Enumerate all builders and set the local SDM as their build status updater

Try create spring in sample-sdm and don't enter rootPackage. The parameter isn't prompted.

Automation client claims in logs it "cannot post to" listener endpoints, but all expected messages are received

We could pull command metadata and generate CLI completions from it at the time when we initialize yargs.

version gets bound as a boolean

Add git merge and fetch hooks

Fetch hooks should return information about committer if available.

Should parse Slack response to get actionable messages. Affects demon.

Local lifecycle should use nicer goal rendering. Should investigate reuse of code from lifecycle project.

This will enable local SDM to notify itself, e.g. of builds, using the regular payload structure.

This will preserve the promise of no code changes to switch to connecting to Atomist service.

Allow env var / config / override on command line

I clicked a button in one of my messages. The command failed, and nothing was sent to the listen terminal.
It should say that it failed. Probably also say something on start and complete.

• Should we remove the environment variables to make it easier to set up?
• Should we introduce a JSON config?
• How can we switch from local SDM to a cloud SDM with minimal change?
• Is SDM a project that can run your code or a module that your code brings in?
• Can you run more than one local SDM? How are slalom commands resolved?

Runs a generator from within Slalom

First action is to create an SDM project, specifying repo tree and name

Affects Spring support.

When editing many projects with local deployment enabled, it's possible to end up with a huge number of deployments and massive memory usage. Need some safeguard to avoid this.

Note: this code is currently in sample-sdm.

See localPostProcess:137, where invokeCommandHandler is invoked

This probably means having a distinct SDM with no other responsibilities. We could have an embedded SDM. Otherwise the SDM would need to shut itself down

Enable people to rev seeds without committing

Avoid extra commit

Put in a script?

Use npm search atomist extension pack node

Parse result, allow selection and provide a transform