The documentation for application manifests specifies an option named magicFutureSetting, yet doesn't describe what it does.
What does this property do?
Just a guess, but it looks to me like a way to test that some setting in the future can be included then accessed via an API like https://msdn.microsoft.com/en-us/library/windows/desktop/aa375700(v=vs.85).aspx
Related
I was looking for a configuration parser for go and https://github.com/spf13/viper seems to come highly recommended.
I am very surprised to find that configuration files are not validated by default.
Viper parses files and extracts requested values from them but I cannot find a way to detect bad configuration.
For instance I if create a (Java style) .properties file containing just "???" and nothing else. This is accepted without any error.
I can understand the philosophy that you should ignore irrelevant configuration items but I desire more rigor. I would also like to reject anything that does not match the X=Y format in a properties file.
To me this is a fatal flaw that suggests I should use a different package (or roll my own as usual).
Have I missed something? Does viper in fact support detecting and rejecting bad configuration keys?
I think the answer is no. viper does not validate java .properties files.
I posted a bug report (or feature request depending on your point of view) as https://github.com/spf13/viper/issues/790
You can try https://github.com/num30/config library which is based on Viper. It has built-in validation.
I've recently updated my serverless project, and I've found that many things have changed in the last few updates.
https://serverless.com/
I don't fully understand whats the correct way to have multiple lambda functions and api gateway endpoints related to the same project. With the old serverless I have every lambda and endpoint as a completely seperate function, this worked pretty well for me.
I can't seem to do this anymore, if I try my second lambda function overrides my first, presumably because my "service name" for both is the same. My service name is the same because I want both rest endpoints in the same API in API Gateway. Since serverless creates the API name based on the service name.
So then I tried to add both functions to the same "Service". this worked for the most part, except that now I need to include my custom role statement for all my functions into the same role (because this one role is now being linked to all my functions). Effectively giving more permissions to each individual function than it should have. The other issue is that all my handler files for the different functions are being put into each functions deployment bundle.
So basically, I'm not sure what is the correct approach to have multiple functions that relate to the same project but are separate in functionality. It used to make sense, now doesn't.
If anybody can give me some pointers please
Thanks
I understand your frustration. I had the same feeling until I looked deeper into the new version and formed a better understanding. One thing to note though, is the new version is not completely finished yet. So if something is completely missing, you can file an issue and have it prioritized before 1.0 is out.
You are supposed to define multiple functions under the same service under the functions: section of serverless.yml. To package these functions individually (exclude code for other functions) you will have to set individually: true under package: section. You can then use include and exclude options at the root level and at the function level as well. There's an upcoming change that will let you use glob syntax in your include and exclude options (example **/*-fn.js). You can find more about packaging here https://www.serverless.com/framework/docs/providers/aws/guide/deploying.
Not sure how to use different roles for different functions under the same service.. How did you do it with 0.5?
I was trying to find a solution for individual iam roles per function as well. I couldn't find a way to do it, but while I was looking through the documentation I found the line: "Support for separate IAM Roles per function is coming soon." on this page, so at least we know they are working on it.
The "IAM Roles Per Function" plugin for Serverless allows you to do exactly what it says on the tin: specify roles for each function. You can still use the provider-level roles as well:
By default, function level iamRoleStatements override the provider level definition. It is also possible to inherit the provider level definition by specifying the option iamRoleStatementsInherit: true
EDIT: You can also apply a predefined AWS role at both the provider and function level.
Is there a way to see TeamCity configurations that override parameter defined in template?
I don't think so. What's worked for me in the past was to search through the project files on the filesystem. If you have many build configs, this will be faster than opening each of them in the GUI.
Search for something like this:
<param name="myParamInheritedFromTemplate" value="myOverrideValue" />
in <TeamCity data directory>/config/projects/**/*.xml. If it's absent in an XML file, that build config just inherits the value. If it's present, it overrides it.
It's hacky but it's quick.
There is a feature request https://youtrack.jetbrains.com/issue/TW-21212, please vote. Current workaround are to either search the raw XML files with the settings stored under TeamCity Data Directory on the server as #sferencik suggested, or use REST API to get settings of all the build configurations and search for the parameter there. Let me know if you need help on any of these.
I am attempting to display a project level property on a widget. Global properties work fine, but project properties come up blank.
I am using:
<%= configuration('sonar.projectlevel.prop1') -%>
in the .erb file, where sonar.projectlevel.prop1 is property name. It comes up blank. If I put in a global property instead of the project property,the property is displayed.
When I open the project dashboard and go into Configuration | Settings, I can see the project property and the value. I can also retrieve it using the ws properties api specifying the resource name, so the value must be there.
Should this work? If so, how?
I have also posted this question to the mailing, but have not had a response. Surely this can work and is easy to do. I must be missing something simple.
Thanks, Ben
Simon Brandhof replied to the mailing list question with the solution. To display a project level property in a widget use:
Property.value('sonar.projectlevel.prop1', #project.id)
instead of:
configuration('sonar.projectlevel.prop1')
Thanks Simon!
I am making a new biztalk solution, where i am using existing maps, schemas and orchestrations. And the orchestrations is giving me lots of problems.
I get this erorr message when I try to build my orchestration:
a 'module' must have a non-null XmlNamespace under BPEL4WS compliance
I can't find any solution to it anywhere, so I hope somebody can help me here.
What does that error mean and how do I solve it??
It turned out that if I clicked on the Project name, there is a BPEL Compliance that was set to True. Should have been set to false.
This doesn't look familiar at all.
Right click on the project and hit properties. Check to see if your assembly namespace and name are set in the 'Application' tab.
Open the orchestration and click on the background between the port surfaces. Check the namespace in the properties window.
If that doesn't work perhaps you can temporarily remove items from the orchestration to see if you can isolate which shape is causing the error.
I have had very strange issues where the orchestration namespace was incorrect.
Some projects require the BPEL Compliance setting to be true. For those projects you may have two cases:
If you do not wish to export the orchestration as a module; make sure the Module Exportable setting is false.
If you wish to export the orchestration as a module; make sure the Module Exportable setting is true together with a Module XML Target Namespace setting that has a valid value instead of being empty (or null)