fugue | Unicorn for node.js - Heavily inspired by Spark and Unicorn

I want to randomly disrupt the order of the letters that make up words in sentences. I can do the shuffling for single words, e.g.:

I am trying to create a JiraRestClient using Basic authentication.

[1] I am having a hard time finding the right JIRA SDK version. I want this StatusCategory class, but I do not find the right jar file containing it.

https://docs.atlassian.com/DAC/javadoc/jira/reference/com/atlassian/jira/issue/status/category/StatusCategory.html

[2] I downloaded the Atlassian JIRA SDK according to their description, but I do not find the jar file in there. Maybe I looked wrong?

https://marketplace.atlassian.com/apps/1210950/atlassian-plugin-sdk-windows/version-history

[3] I also tried to find the JAR file using mvnrespository.com, but no luck, all dependencies are scoped with provided.

https://mvnrepository.com/artifact/com.atlassian.jira/jira-api

[4] Previously, I used an old version of the JIRA API, which worked, but it does not contain the StatusCategory class, which I want.

I am facing issue related to Search JQL. I am using the query

I have the following task:

Guidelines: You may implement your solution in Java/C#.

1. You are asked to implement the EntityCollection interface which is specified in the attached Java file.
2. Your implementation should support the following operations:
   a. Add - adds the entity which is given as input to the collection.
   b. Remove Max Value - removes the entity with the maximal value from the collection and returns it.

3. You should provide 3 implementations for the following use-cases (A-C), according to the frequencies of performing Add & Remove Max Value in these use-cases:

Each use-case implementation should be optimized in terms of its WC time complexity -

• If one operation is more frequent than the other operation (e.g. high vs. low) – then the frequent operation should have the lowest possible complexity, whereas the other operation may have higher complexity but still optimized as much as possible.

• If both operations are equally frequent (e.g. medium vs. medium) – then both should have similar complexity, which is as low as possible in each operation while taking into account also the need for the same complexity in the other operation.

The given java code:

...

We are dealing with the problem of providing build time and run time secrets to our applications built using AWS CodePipeline and being deployed to ECS.

Ultimately, our vision is to create a generic pipeline for each of our applications that achieves the following goals:

• Complete separation of access
  • The services in the app-a-pipeline CANNOT access any of the credentials or use any of the keys used in the app-b-pipeline and visa-versa
• Secret management by assigned developers
  • Only developers responsible for app-a may read and write secrets for app-a

Here are the issues at hand:

• Some of our applications require access to private repositories for dependency resolution at build time For example, our java applications require access to a private maven repository to successfully build
• Some of our applications require database access credentials at runtime For example, the servlet container running our app requires an .xml configuration file containing credentials to find and access databases

Along with some caveats:

• Our codebase resides in a public repository. We do not want to expose secrets by putting either the plaintext or the cyphertext of the secret in our repository
• We do not want to bake runtime secrets into our Docker images created in CodeBuild even if ECR access is restricted
• The Cloudformation template for the ECS resources and its associated parameter file reside in the public repository in plaintext. This eliminates the possibility of passing runtime secrets to the ECS Cloudformation template through parameters (As far as I understand)

We have considered using tools like credstash to help with managing credentials. This solution requires that both CodeBuild and ECS task instances have the ability to use the AWS CLI. As to avoid shuffling around more credentials, we decided that it might be best to assign privileged roles to instances that require the use of AWS CLI. That way, the CLI can infer credentials from the role in the instances metadata

We have tried to devise a way to manage our secrets given these restrictions. For each app, we create a pipeline. Using a Cloudformation template, we create:

• 4 resources:

  • DynamoDB credential table
  • KMS credential key
  • ECR repo
  • CodePipeline (Build, deploy, etc)

• 3 roles:

  • CodeBuildRole Read access to DynamoDB credential table Decrypt permission with KMS key Write to ECR repo
  • ECSTaskRole Read access to DynamoDB credential table Decrypt permission with KMS key Read from ECR repo
  • DeveloperRole Read and write access to DynamoDB credential table Encrypt and decrypt permission with KMS key

The CodeBuild step of the CodePipeline assumes the CodeBuildRole to allow it to read build time secrets from the credential table. CodeBuild then builds the project and generates a Docker Image which it pushes to ECR. Eventually, the deploy step creates an ECS service using the Cloudformation template and the accompanying parameter file present in the projects public repository The ECS task definition includes assuming the ECSTaskRole to allow the tasks to read runtime secrets from the credential table and to pull the required image from ECR.

Here is a simple diagram of the AWS resources and their relationships as stated above

Our current proposed solution has the following issues:

• Role heavy
  • Creating roles is a privileged action in our organization. Not all developers who try to create the above pipeline will have permission to create the necessary roles
• Manual assumption of DeveloperRole:
  • As it stands, developers would need to manually assume the DeveloperRole. We toyed with the idea of passing in a list of developer user ARNs as a parameter to the pipeline Cloudformation template. Does Cloudformation have a mechanism to assign a role or policy to a specified user?

Is there a more well established way to pass secrets around in CodePipeline that we might be overlooking, or is this the best we can get?

I'm working with ng2 and kendo-ui grid component. I've had no issues until I went to add another property to kendo grid component, and now I seem to be stuck in some strange compiler fugue state.

Error in Chrome Dev console:

i want to connect to my jira instance in java via Rest-Api. That's why i implement first the connection to the host.

I read a lot of tutorials and i found JRJC. But nothing has worked.

*updated

i have a accordion Menu and some stylesheets.

my css and menu.php