How can i override <history-level>full</history-level> to <history-level>activity</history-level> in camunda using cli(jboss cli)
finally following works for me.
/subsystem=subsytem_name/process-engines=default:write-attribute(name=history-level,value=activity)
Related
Really stumped right now. I want to use Amplify for a Cloud assignment and have done amplify init in VS Code terminal to create the app. Unfortunately, I've been receiving this error when I try to enable Amplify Studio via the AWS webpage.
I thought my roles and permissions might need to be adjusted but I have AdministratorAccess-Amplify on the users I need. I also couldn't delete any of my test applications due to a similar error, but I managed to delete them via the CLI with no issues.
So my question is, is there any way to enable Amplify Studio via the CLI, or has anyone run into this issue before and been able to fix it?
Thanks in advance.
:)
When I do an operation like an S3 upload, using the AWS GUI from browser, is it possible to retrieve the relative CLI command for generating the same operation already done?
Thanks.
There is an extension for chrome and Firefox (As far as I know) that records the changes made in the AWS console and translates it to CLI commands.
Plugin Link
Although not all the services / actions are supported It does a pretty good job. Here you can check the service coverage of the plugin
Service Coverage
I'm trying to write simple CLI tool, helping me with several VSTS-related tasks, like:
Create project from template
Building and watching build from console
etc
So, it would be nice to attach to running build (triggered via CI) and watch console output in live in my desktop console. Is there such ability in SDK?
I'm currently using this packages:
https://www.visualstudio.com/en-us/docs/integrate/get-started/client-libraries/dotnet
There isn't any API can achieve this feature as I know. You can submit a feature request on VSTS User Voice.
I am new to Amazon simple workflow service and am following AWS Docs to understand SWF.
As per the documentation, once you execute the GreeterMain class after executing the GreeterWorker class, you should see active workflow execution on AWS console. However thats not the case with me. On executing the GreeeterMain class, the application prints out Hello World but I do not see any active workflows in "My Worfkflow Executions" sections on AWS console. I am not getting any errors as well.
On executing the GreeterWorker class, I can see "Workflow Types" and "Activities Types" section populated with appropriate workflows and activities.
Am I doing something wrong? Can someone please help out.
Thanks.
Ahh.. Found it.... As per doc, you create class with name "GreeterMain" in two different packages. One package is basic code path, second uses AWS SWF. While executing Eclipse was referring to basic code path and not invoking AWS SWF.
I have log statements in my mapper using slf4j/log4j that are not showing up in application(port 8090) logs.
Do I have to configure anything for this in hadoop 2.x? Everything works well in 1.x
Thanks in advance for your help.
Logging works bit differently in Hadoop 2.x
Please follow steps mentioned below:
1.You will find container-log4j.properties in hadoop-yarn-server-nodemanager jar file, extract it (make your Custom changes) and run below command
jar uf /home/hadoop/share/hadoop/yarn/hadoop-yarn-server-nodemanager-2.2.0.jar container-log4j.properties
2.Alternatively yo can make changes in file hadoop-config.sh(you can specify custom changes for logger in line below)
HADOOP_OPTS="$HADOOP_OPTS -Dhadoop.root.logger=${HADOOP_ROOT_LOGGER:-INFO,console}"