Array/object parameter in octopus custom step template - octopus-deploy

Is there a way to add array/object parameter to octopus custom step template?
Built in step "Deploy to IIS" allows to add collection of bindings. Can such functionality be added to a custom step?

I don't think it's possible to setup an array parameter for a custom step template. See Custom Step Templates documentation.
You could put an array into a variable and parse that with Powershell. Also, here is a custom step template example.
You could reach out to Octopus Support to see if they have any other recommendations or maybe add it to their UserVoice to see if others are interested in the feature.

Related

How do I specify the "Trigger" value when starting a Google Cloud build using the projects.triggers.run API

In the builds web UI there is a column labeled "Trigger". For automatically triggered builds it has the value "Push to branch-name branch". This was added recently and is very useful.
I want to add the same (or a similar value) that displays in that column when I use the projects.triggers.run API to run a trigger through the API. I looked at the help page here but I cannot see a way. Is there a way that maybe is not documented yet?
The way to run that trigger would be to specify the Trigger ID. If you were to follow the trigger that links to, the url is in the form ".../cloud-build/triggers/$TRIGGER_ID/..", so you could use that to get the ID.
Best,
Ben

SonarQube - Add parameters to rule via API

Using SonarQube 6.0, it seems that you are unable to add parameters to rules unless they are custom. Some rules that come with plugins allow parameters, however there seems to be no way to provide these. Also, it appears that you cannot copy a rule to make it custom and add parameters that way.
One such rule:
https://github.com/SonarSource/sonar-javascript/blob/master/javascript-checks/src/main/java/org/sonar/javascript/checks/UntrustedContentCheck.java
Any way to achieve this via the API?
Thanks

Add a sonar rule to forbid use of URL GET parameter

I would like to add a Sonar rule to forbid use of URL GET parameters.
I mean I only want to allow POST parameters in my application forms.
Can you help me to write this rule ?
Since the Web plugin doesn't support custom rules, you'll need to either write your own supplementary plugin (i.e. use the Web plugin plus the one providing your custom rule(s)) or submit a pull request to add your rule directly to the plugin. In either of those cases, you should probably look to the SonarQube Google Group for further discussion/guidance.
You didn't specify the language you want to analyse, but depending on which one you're using you can use XPath to analyse the syntax tree. If XPath isn't supported for your language you'll really have to write your own custom plugin like said in the other answer.
See here for each language support:
SonarDocs - Writing Custom Rules
If you do need to write a custom plugin, I can only recommend you to take a look at the existing code, starting with java.custom-rules

Dynamics CRM Managed Solution Add Customer Set Parameters

I'm creating a solution which will be released as a managed solution for Dynamics CRM Online.
However, the customer will need to put information in when installing the managed solution to allow interaction with outside services.
For example, when you install the LinkedIn solution, you need to add your log in information to allow the CRM to access your LinkedIn account.
How do I add these parameters to the a solution, and then allow the customer to update them if they change?
Cheers
Edit:
To add to my query and following the answer below.
To make sure the process is correct in my head.
Option 1.
I will create a custom entity for storing key/value, or username/password combination.
I would then create a customisation page for the solution using html web resource, which when submitted, javascript would create a single record to hold those values.
I then need to link every record that needs the values stored in the custom record - I'm not sure how this would be done without editing a workflow after the storage record has been created, to link each normal record to the storage one.
Option 2.
Create an xml web resource that stores the values. Create the html/javascript resources to update this using the configuration page.
I can then use a javascript function to obtain that data when the custom entity is created, perhaps to populate hidden fields for storage and use behind the scenes.
I can't find any tutorials on getting started with using xml in this way - can you point me in the right direction?
I typically create a "Configuration" entity that has Name/Value attributes. This is also useful when you have Dev/Test/Prod environments that require different configs (e.g. URLs, credentials, etc).
Another approach is to using Plug-in configurations or Web Resources to store that type of information. The Plug-in configuration is pretty straightforward if you can have the customer use the Plug-in Registration tool to modify the value.

Custom fields in Sonar

I've looked at Sonar for a way to include custom fields for grouping/filtering data on-the-fly, including at addon extension points, but haven't seen anything that meets my criteria.
For example, for a multi-team project where all teams share the same repository project, I'd like to be able to filter the standard reports for single teams (encoding the team data for instance in a custom java annotation).
Is this possible? If so, how?
According to this discussion on the mailinglist: http://thread.gmane.org/gmane.comp.java.sonar.general/10059 ... http://thread.gmane.org/gmane.comp.java.sonar.general/10073
It is not possibile to have group-specific dashboards/reports/views. The only thing supported right now are filters.
I'm not aware of any custom solution.

Resources