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.

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

[SET-627] Enable chatter #137

Merged
merged 1 commit into from
May 8, 2024
Merged

Conversation

nicolasbock
Copy link
Collaborator

This change adds a configuration option to post comments to a chatter
object instead of a casecomment object. The feature is disabled by
default and has to be explicitly enabled via the configuration file:

salesforce:
  enable-chatter: true

The change also introduces the salesforce-test binary to test
Salesforce queries.

Closes: SET-627
Signed-off-by: Nicolas Bock [email protected]

@nicolasbock nicolasbock self-assigned this May 7, 2024
@nicolasbock nicolasbock force-pushed the set-627 branch 5 times, most recently from 7144d95 to e9a493a Compare May 7, 2024 19:55
@nicolasbock nicolasbock force-pushed the set-627 branch 2 times, most recently from ab975a2 to 3dbba2a Compare May 7, 2024 20:27
This change adds a configuration option to post comments to a chatter
object instead of a casecomment object. The feature is disabled by
default and has to be explicitly enabled via the configuration file:

```yaml
salesforce:
  enable-chatter: true
```

Closes: SET-627
Signed-off-by: Nicolas Bock <[email protected]>
Copy link

@KellenRenshaw KellenRenshaw left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Aside from some extra formatting changes, LGTM.

@nicolasbock nicolasbock merged commit bb26ce5 into canonical:main May 8, 2024
4 checks passed
@nicolasbock nicolasbock deleted the set-627 branch May 8, 2024 13:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants